Label error. Requires exactly 1 of: changelog:.*. Found: 🖥️web. A maintainer will add the required label.

Great work on adding support for setting the timestamp with seconds — this is already a very useful improvement!

One thought: many images already store their capture time in EXIF with both seconds and sub-second precision. For example, using exiftool, you’ll often see something like:

Date/Time Original              : 2025:08:06 16:33:49
Offset Time                     : +02:00
Offset Time Original            : +02:00
Sub Sec Time Original           : 220

–– Composite ––
Date/Time Original              : 2025:08:06 16:33:49.220+02:00

The composite tag combines exif:DateTimeOriginal and exif:SubSecTimeOriginal to preserve millisecond precision.

When changing the timestamp in the UI, Immich typically writes a composite timecode to exif:DateTimeOriginal and photoshop:DateCreated in the XMP sidecar.

If the timestamp edit function could handle both seconds and milliseconds (three digits), it would ensure that we maintain the original sub-second accuracy already present in many images, rather than truncating this information. This would be especially beneficial for workflows where precise capture time matters (e.g., burst sequences, sports, scientific imaging).

Have you considered including this in your implementation?

@trommegutten suggestion seems easy to implement. Working on test instance:

Checklist:

• I have made corresponding changes to the documentation if applicable
• I have no unrelated changes in the PR.
• I have confirmed that any new dependencies are strictly necessary.
• I have written tests for new code (if applicable)
• I have followed naming conventions/patterns in the surrounding code
• All code in src/services/ uses repositories implementations for database calls, filesystem operations, etc.
• All code in src/repositories/ is pretty basic/simple and does not have any immich specific logic (that belongs in src/services/)